Thanks @minhsueh! I updated the testing workflow to run for the currently supported python versions. Could you check the test output to see if you can figure out why they're failing now? Thanks! Tagging @mkhorton here, too. Maybe we'll be lucky and has a few spare minutes to help out with this PR :)

@tschaume It looks like a compatibility issue between selenium and urllib. The previous successful tests do not specify a Selenium version.

Ref:

1. https://stackoverflow.com/questions/76614392/getting-error-when-i-run-selenium-script-value-error-timeout-value-connect-was
2. https://stackoverflow.com/questions/78167430/selenium-error-timeout-value-connect-was-object-object-at-0x000002b530c948b0

@minhsueh I pinned the selenium and urllib3 dependencies, and updated the requirement files in the main branch. The connection error in the tests is gone now. There seems to be legitimate but potentially unrelated reasons why the tests are still failing now. Could you take a closer look when you get the chance? Thanks!

@tschaume fixed the tests! #479